Skip to content

Pod Level Identity Support For JFrog Artifactory on GCP#54

Open
oumkale wants to merge 1 commit intomainfrom
kep-gcp
Open

Pod Level Identity Support For JFrog Artifactory on GCP#54
oumkale wants to merge 1 commit intomainfrom
kep-gcp

Conversation

@oumkale
Copy link
Member

@oumkale oumkale commented Mar 12, 2026

Pod Level Identity Support For JFrog Artifactory on GCP:

Traditionally, Kubernetes kubelet used a single "Node-level" identity to pull images. KEP-4412 enables a move to Pod-level identity, where the Kubelet uses a Pod's own ServiceAccount token to authorize image pulls.

For teams running JFrog Artifactory on Google Cloud (GCP), this configuration allows the JFrog Credential Provider to leverage GKE Workload Identity. The Kubelet generates a token for the Pod's identity, which the JFrog plugin then uses to authenticate with Artifactory, ensuring that image pull permissions are tied directly to the specific workload.

[ WORKLOAD POD ]
       | (Uses KSA)
       v
[   KUBELET    ] <--- Requests JWT for Audience: identityconfig.googleapis.com ---> [ K8s API SERVER ]
       |
       | (Executes Plugin with JWT)
       v
[ JFROG PLUGIN ] <--- Exchanges K8s JWT for Access Token ---------------> [ GCP STS / IAM ]
       |
       | (Requests Registry Credentials)
       v
[ ARTIFACTORY  ] <--- Validates Identity and provides Pull Token
       |
       | (Returns Credentials to Kubelet)
       v
[   KUBELET    ] <--- Performs Docker Pull -----------------------------> [ ARTIFACTORY ]

Signed-off-by: oumk <oumk@jfrog.com>
@oumkale oumkale self-assigned this Mar 12, 2026
@oumkale oumkale requested a review from a team March 12, 2026 08:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant